MarchThe effective date for all products within the scope of this document for this release is March 9 for the CT environment and March 16 for the Production environment.
| Upgrade to support Organizations, Policy and Product Setup Application and Webservices |
|---|
- Type: New Feature
- Reference: N/A
- Compliance Impacts: This item is not a compliance or regulatory issue.
- Documentation Impacts: No documentation impact
|
| Summary: The Organizations, Policy, and Product Setup Application (OPPSA) and OPPSA Webservices are now available for use with Expere Document Services. |
| Implementation Notes:
|
2017.1The effective date for OPPSA within the scope of this document for this release is TBD. This release utilizes OPPSA version 17.1.0.808.
| OPPSA webhelp URL updated |
|---|
- Type: Enhancement
- Reference: PBI 442392
- Compliance Impacts: This item is not a compliance or regulatory issue.
- Documentation Impacts: No documentation impact
|
Summary: The OPPSA user guide has been converted to a a new content management system and the URL has changed. For future deploys of the OPPSA application, modify the Transform.xml file and update the value to the new URL for property ""OPPSA.WebHelpLink". |
Implementation Notes: To access this updated URL immediately from the OPPSA application (HELP Link), modify the web.config file and update the OPPSA.WebHelpLink value to the new URL. Example:<Property Id="OPPSA.WebHelpLink"
Value="https://documentation.wolterskluwerfs.com/Help/OPPSA/" />
|
| Security enhancement for IntegrationService methods |
|---|
- Type: Enhancement
- Reference: PBI 436677
- Compliance Impacts: This item is not a compliance or regulatory issue.
- Documentation Impacts: No documentation impact
|
Summary: IntegrationServices methods are now only available through the HTTPS secure communication protocol which requires an SSL certificate. |
Technical Notes: The following OPPSA IntegrationServices methods are affected:- GetOrganizations
- GetProductsForOrgGuid
- MergeProductData
|
| Implementation Notes: The WSDL has been updated and users must regenerate the OPPSA Integration Service and install the latest version of OPPSA and Document Generation Services. |
| OPPSA Barcode handling |
|---|
- Type: Defect Correction
- Reference: PBI 421221 / 416779
- Compliance Impacts: This item is not a compliance or regulatory issue.
- Documentation Impacts: No documentation impact
|
Summary: The system was displaying the following error to the user when selecting the Barcode Preview option in OPPSA:- Server Error in '/OPPSA' Application
|
| Technical Notes: This is now resolved. See Document Generation Services 2017 Change Log - OPPSA Barcode Previews for more details. |
| Implementation Notes: No user action is necessary. |
| Load Balancing for OPPSA |
|---|
- Type: Enhancement
- Reference: PBI 425295, 423298
- Compliance Impacts: This item is not a compliance or regulatory issue.
- Documentation Impacts: No documentation impact
|
| Summary: The OPPSA Application can now be load balanced. Previously, Organization data was not cached per instance of Expere. A new property has been added to the Document Generation Services installation that allows for configuring the cache for load balanced environments. |
| Implementation Notes: See Expere Engine Change Log Entry 423298: Caching database organizations configurable. |
| New Parameters Added to Expere DB Install Script to Configure DomainAccount User Permissions |
|---|
- Type: New Feature
- Reference: PBI 426693
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation Impacts: Install Expere Database
|
Summary: For new OPPSA installations where an Expere Database needs to be created, the InstallExpereDM.ps1 script has been modified to accept the following parameters. - ACCOUNTDOMAIN
- DOMAINACCOUNT
This script utilizes these parameters to configure the DOCGEN Database DomainAccount user to have the following Database roles for the Expere Database (db_datareader, db_datawrite, db_owner). Prior to this change, configuring the DomainAccount user to have access rights to the Expere Database was a manual step. |
| Implementation Notes: New parameters: See Install Expere Database for additional information. |
| Minimum Password Age |
|---|
- Type: Enhancement
- Reference: PBI 413146
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: OPPSA User Guide updated.
|
| Summary: The system has been modified to track password change date/time and validates against a minimum password age. The change password feature checks the last password change and prevents the user from changing the password if it does not exceed the minimum password age and displays the following message: “Password cannot be changed prior to x days of the last password change (mm/dd/yyyy hh:mm:ss: am/pm).” |
| Technical Notes: The minimum password age is a configurable property available to set during the OPPSA Application Installation (Transform Property: <Property Id="OPPSA.MinPasswordAgeInDays" Value="0" />. See Modify Transform.xml File for specific value details). |
| Implementation Notes: This validation does not occur for first time users who are required to perform a password change or for users that had their password reset by their System Administrator. The ‘Forgot Password’ feature requires the user to change their password as part of that workflow and cannot be used if the last password change does not exceed the minimum password age. The following message displays if this scenario occurs: “Unable to use Forgot Password feature. Password cannot be changed prior to X days of the last password change (mm/dd/yyyy hh:mm:ss am/pm). Please contact your System Administrator to Reset Password.” |
| User Login Lockout Attempts |
|---|
- Type: Enhancement
- Reference: PBI 413146
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: OPPSA User Guide updated.
|
| Summary: The Login page logic has been modified to count failed attempts using the value for the configurable property: MaxPasswordAnswerAttempts. For example, if the configuration value is set to ‘5’, the user account will lock after the 5th failed login attempt (previously it was locking after 6th failed login attempt). |
| Implementation Notes: The MaxPasswordAnswerAttempts is a configurable property available to set during the OPPSA Application Installation. See Modify Transform.xml File for details. |
| Log Authorization Events |
|---|
- Type: Enhancement
- Reference: PBI 413164, 414682
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: OPPSA User Guide updated.
|
Summary: The authorization service functions have been modified to capture the following events in the security log file: - Create User
- Change Password
- Assign Roles To User
- Remove Roles From User
- Reset Password
- Enable User
- Disable User
- Unlock User
- Delete User
- Does User Exist
- Change Challenge Question And Answer
- Reset And Get Temporary Password
- Get User
- Create Roles
- Get Roles
- Delete Roles
|
| TIN Field Data Mask |
|---|
- Type: Enhancement
- Reference: PBI 413219
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: OPPSA User Guide updated.
|
| Summary: The Tax Identification Number (TIN) on the Charter page is now masked. During data entry, the values display and upon leaving the field, the value is masked with asterisks. |
| Renaming Policy Retains Policy If Use Existing Name |
|---|
- Type: Enhancement
- Reference: PBI 422490
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: OPPSA User Guide updated.
|
| Summary: Previously, if a policy was renamed using a policy name that already exists, the application deleted the policy being renamed from the database and displayed an error message stating that the policy name already exists. |
| Enhancement: The policy rename function has been modified to retain the policy in the database when trying to rename it using an existing policy name. The error message text has been enhanced as follows: “Updates were not saved. The Policy Name already exists.” |
| Messaging when creating new barcode if already exists |
|---|
- Type: Enhancement
- Reference: PBI 423048
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: OPPSA User Guide updated.
|
| Summary: Only one barcode can exist per organization (excludes inherited barcodes). Previously, if a barcode already existed for a given organization and the user attempts to add another barcode (+Barcode button), a fault exception message displayed. |
| Enhancement: The process has been modified and the following message displays if the user attempts to add a barcode for an organization where one already exists: "Unable to create barcode. A barcode already exists for this organization. Please update the existing barcode." |
| Health Check Page for OPPSA Service/Application |
|---|
- Type: Enhancement
- Reference: PBI 407743
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: OPPSA User Guide updated.
|
| Summary: A Health Check Page is available for use to check the status of the OPPSA service/application. |
Technical Notes: Health Check Page URL: https://example.domain.net/OPPSA/HealthCheck.aspx (replace “example.domain.net” with fully qualified server name. ); the following connections are checked: - Expere Endpoint
- SQL Server Database Access
- Integration Service Endpoint
|
| Application Session Timeout |
|---|
- Type: Enhancement
- Reference: PBI 413150
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: OPPSA User Guide updated.
|
| Summary: A session timeout of 20 minutes has been added to the OPPSA application. The session will automatically end after 20 minutes of inactivity and display the following message: “For security reasons, your session is no longer active. Click Continue to proceed to login page.” |
| Implementation Notes: The session timeout value is not a configurable property. |